WinDesk 95 - An MPC Encyclopedia/WinDesk 95 - An MPC Encyclopedia.iso/power/lstrial2.000/lspak.exe/LSCONFIG.DOC

Text File | 1995-08-26 | 28KB | 589 lines

                              -= [ LSConfig ] =-

                        LightSpeed Configuration Utility

                           Pre-Release Trial Edition

 Copyright (C) 1995 by RidgeLine Corporation [phone] Fax: [phone]



    LSConfig is a utility program which lets you easily modify the settings
  used by LightSpeed.  It is also the only way to setup your BBS's file and
  mail areas, security classes, and system events.  It also serves the final
  purpose of controlling your LaserLink systems, but LaserLink is untested
  and most likely unstable in the Pre-Release version of LightSpeed.

    The documentation for LSConfig is abbreviated and incomplete in this
  pre-release version, however it covers all the major options effectively.
  We also apologize for the lack of a help system in LSConfig, however we
  plan to add one soon.

    LSConfig uses two interfaces.  Some windows like the Master Setup are
  obvious and just ask for your input.  However, other windows like the
  Nodes Setup are more complicated.  Node Setup, Security Classes, Mail
  Areas, and File Areas all use this interface.  In these windows, you can
  use the [INS] or [Insert] keys to insert a new item, and use the [DEL]
  or [Delete] keys to delete an item.  In most of these windows you may hold
  down the [Ctrl] key and press the up or down arrow keys to move items
  around.  To modify an item, position your cursor on top of it using the
  up and down arrow keys and press [Enter] or [Return].

    There are some places where you will need to press [Space] or [Enter]
  to be given a list of options to choose from.  These are called
  "Select Boxes".  When you have a Select Box open, press ESC to leave your
  choice as it was, or press the number before the selection you wish to
  make.

    [ Master Setup ]

  Name of BBS:      [Self-Explainatory]
  Sysop Alias:

    This option defines what the sysop will be known as on the system.  When
  a user tries to write a message to "Sysop" it will be redirected to this
  alias.  You can also do a modem or local logon with this alias, and you
  will be using the same account as a sysop logon.  You will have to create
  this account the first time you logon to your system.

  Ramdrive letter:

    This is the drive letter of your ram-drive, if you created/have one.
  If you do not wish to use a ram-drive, just set this to the same drive
  LightSpeed can be found on.

  Page level:

    This is a number, usually around 4, which defines how many times
  LightSpeed will ring the page bell.  If you find the page the sysop to be
  too loud or long, just reduce this value.  Or if you have trouble hearing
  the sysop page, increase this value.

  Message age -> See Ls.Doc under [Part II - Mail System - The details...]

    [ Nodes Setup ]

    For as many nodes as your system has, you will need one item here.  The
  trial edition of LightSpeed supports up to 2 nodes, 1 of which can only be
  for local use (The sysop may have his or her own private node.)  If you
  wish to setup for 2 nodes, create 2 items here (If you see "No entries..."
  then press Insert twice.)  You may create only a single node if you wish.
  (Note that there is nothing to prevent you from creating more than 2 nodes
  here, however LightSpeed will not operate with more than 2.)
    Once you have created one or two nodes, select one and press ENTER on
  it.

    [ Node Setup ]

  Name of node:          [This is for your own use, LightSpeed ignores it]
  Door swapping:            [How to "swap out", disabled in Trial Edition]
  Temporary (Swap) directory:       [Where temp files should go, disabled]
  Comm Routines:                                              [Select Box]

    Commonly, BBS software use two methods to communicate with a modem.  The
  first is called a "Fossil Driver".  Fossil drivers are TSR programs that
  are loaded before your BBS, often in your Config.Sys file when your
  computer first starts up.  Some BBS Softwares REQUIRE this fossil driver.
  And because of that, many door programs also require or support fossil
  drivers.  However, it is also possible to load a fossil driver for a
  specific door, which means you can turn fossils on and off as needed.
    The other method is called "Internal Comm Routines" which means
  LightSpeed communicates directly with the modem instead of talking
  "through" a fossil.
    Both methods will work with LightSpeed, however using a fossil would
  require extra setup.  Some doors will operate faster with a fossil than
  by themselves, however LightSpeed will operate just as fast with either.
  It is therefore highly recommended that you use Internal Comm Routines
  with LightSpeed.
    You can leave this option as "Autodetect" which means that LightSpeed
  will use a fossil if one is loaded, however it is better that you don't.

  UART Type:                                                  [Select Box]

    This option can almost always be left as "Autodetect".
    All standard modems have either an 8250 or 16550 UART chip in them.  The
  16550 chip is prefered and faster, however it is rarely found on external
  modems.  This option is only needed if you are CERTAIN that LightSpeed is
  mis-detecting the chip in your modem.  This is a very rare occurance.

  Comport:

    This option is most important in selecting if this node will be "Local"
  or "Online".  To make the node local, set this to 0.  Otherwise, the node
  will be Online.  If you are using a standard comport number (COM1 through
  COM4) place the number here.  If you are not using a standard comport,
  leave any number here (it is OK to place a 1 here even if you aren't using
  standard COM1, -DO NOT- leave this 0 if you are using a non-standard
  comport.)

  Irq Number:

    If this node is local (Comport is 0) this value is ignored.
    If you are using standard comports COM1 or COM3, set this to 4.
    If you are using standard comports COM2 or COM4, set this to 3.
    You CANNOT use the same IRQ more than once at any one time.  This means
  if you are running 2 nodes simultanously, those 2 nodes cannot share the
  same IRQ.  There are a few exceptions to this if you have special hardware.
    If you are using non-standard comports, you may have to find this
  information elsewhere, refer to your modem manual on internal modems and
  serial I/O card manual for external modems.

  Base Address (Hex):

    If this node is local (Comport is 0) this value is ignored.
    If you are using standard comport COM1, set this to 0x3F8.
    If you are using standard comport COM2, set this to 0x2F8.
    If you are using standard comport COM3, set this to 0x3E8.
    If you are using standard comport COM4, set this to 0x2E8.
    If you are using a non-standard comport, refer the same source as you
  did to find the IRQ.

  Input Buffer (Try 512):

    This defines how many bytes of memory will be set aside to store user's
  input while the system is busy.  512 is usually a perfectly fine setting
  for this, and is an insignificant amount of memory to worry about.

  Input Buffer (Try 5120):

    This defines how many bytes of memory will be set aside to store user's
  output while the user's baud rate is causing slow-down.  5120 is usually
  a perfectly fine setting for this, and is not much memory to worry about.
  (about 1000 to 1500 bytes are normally used in an ansi screen such as a
  menu.)

  Initialize Baud Rate:

    This setting may vary from modem to modem.  If you are using a 14.4k
  modem, it is probably safe to try putting in 19200 for this value and see
  if it works correctly.  (Use 14400 for this value is the same as 19200,
  however 19200 works better.)  If you are using a 28.8k modem you should
  try 28800 for this value.  If you are using a 2400 modem you should
  probably use 2400, and 9600 baud modems should usually use 9600 here.
  If you have problems with your modem, this setting may be the cause.  You
  can also set this setting to 0 and let LightSpeed vary the baud rate for
  each call.  Usually, problems with this setting will show up as garbled
  ANSI or online garbage.

  Modem Reset:                    [Usually ATZ]

    This command is ATZ in most modems, however there may be some exceptions.
  You may need to consult your modem manual if you have problems with this
  setting.  Problems with this setting will most likely cause LightSpeed
  to go into "Retry's" after "Initializing modem" when LightSpeed first
  starts up, HOWEVER, sometimes Retrys are normal.  You have a problem when
  LightSpeed constantly exits after too many retrys.

  Modem Init:                     [Usually AT&F1&C1&D2M0L0E0S0=0]

    This command should also work with most modems, but again there may be
  some exceptions.  You may need to add/remove options from this depending
  on your modem.  The individual commands are as follows:

    &F1 = Modem Init, Software flow control
    &C1&D2 = Variable Modem Carrier, not having this can cause problems in
      some modems, such as carrier detections problems which is used to
      determine when a user connects and hangs up.
    M0 = Modem Speaker Off
    L0 = Modem Speaker Volume Off
    E0 = Modem Echo Off
    S0=0 = Modem Auto-Answer Off (LightSpeed answers the modem itself)

  Modem answer:                  [Almost always ATA]

    This command should work with just about every modem in existance.

    [ General Setup ]

  Type of system:                [Select Box]

    This defines what kind of BBS you will be operating.  Open Questionare
  is the most common choice.

    Open systems are ones where users may logon freely and create their
  own account.  You can still give users reduced security levels on an
  open system until you can manually upgrade their account.  Some BBS'es
  ask you to call back in 24hrs for full access, which gives the sysop
  enough time to scan through all user accounts and check that the
  information given looks legitament.
    Closed systems are more private BBSes where users must have their
  accounts defined by the sysop.  These systems can also allow users to
  call back in 24hrs or so, but they force the sysop to do more work and
  gives users NO access to the system until the 24hrs have passed.

    Open Questionare:  Lets users create an account gathering the necissary
  information in a questionare.
    Open Questionare & Comment:  Lets users create an account gathering the
  necissary information in a questionare, and then forces the user to write
  a comment to the sysop requesting access.

    Closed:  Totally prevents users from logging onto the system without an
  account already defined.  The sysop must enter ALL accounts manually.
    Closed Questionare:  Also prevents users from creating new accounts,
  however this mode can ask some questions before disconnecting the user.
    Closed Comment to Sysop:  This mode lets the user write a comment to the
  sysop before disconnecting the user.

  New user questionare:          [Usually Quest\New.Qst]

    This sets the questionare file that is used whenever a new user logs on
  to the system.  This questionare will also be the one given on
  Closed Questionare systems before disconnecting.

  Environment Size:              [Usually 768]

    This specifies how many bytes Command.Com's spawned by LightSpeed should
  allocate for environment space.  LightSpeed makes extensive use of
  MS-Dos environment variables, so it is recommended that this value be at
  LEAST 768 bytes.  It may be advisable to set it as high as 1024.

  Flag Names:    [Not used in Pre-Release]
  Registery Comment Field:

    The registery of users provides one line that you can change to hold
  whatever information you as the sysop desire.  The setting here is what
  will show up when viewing other user's registeries.  The default is:
  @CS@cign:      (See also Ls.Doc: LightSpeed color codes)

  New User Security:

    This is the name of the security class assigned to new users.  This
  class is assigned to the new users the instant the new user questionare
  begins.  The new user questionare can modify this setting if needed.

  Time for first call:

    This setting determines how much time new users may use the system for
  (in minutes) on their first day using the system.

  Credits given to new users:

    This setting determines how many credits new users will receive to begin
  with.

  Inactivity Timer:

    This setting determines how many minutes the user can go without pressing
  any keys before the user will be logged off automatically.  The recommended
  setting is 5 minutes.

  Hourly Charging   [Subscreen]

    Using this you can modify the rate at which credits will be consumed
  by the hour of the day the user is online.  The setting is in percentage,
  100% would be no change.  The setting does not affect "Charge" menu
  commands, only "Rate" menu commands.  And the Rate is an integer, meaning
  it has no decimal point.  Therefore using a Rate of 5 and setting the
  hourly rate to 99% would just be rounded off back to 5.  This setting
  might be used to encourage users to make more use of the system in less
  busy hours such as 2am-6am.

  Allow leaders to name groups:  [Disabled]
  Credits per dollar:            [Default 1200]

    This setting only affects the Online Upgrade option of LightSpeed, which
  is when the sysop at the local console presses F9 while a user is online.
  After pressing F9 the online upgrade box appears, where you may enter a
  number of credits or money amount.  If you enter a money amount, it will
  be multiplied (by dollar) with the above setting.

  [ Security Setup ]

    All BBS Systems operate using "Security Classes" also called
  "Security Levels."  Each security class defines the general capabilities
  of the BBS users.  All users have exactly one security class which they
  are assigned.  An example of the use of security classes in a average
  BBS System:
    Users are assigned "NewUser" security class when they log on for the
  first time.  This security class expires after 1 week and leaves the user
  with "Demo" security class.  Users with the "NewUser" class have access to
  the system's basic features.  Users with the "Demo" class loose access to
  the system's teleconference and download features.  Anytime a user sends in
  a cash donation the sysop UPGRADES (changes their security class) to
  "Paid" security class.  All users with the "Paid" security class have
  full access to all the system's features until the security class EXPIRES.
  Expiration happens when the user logs-on past the expiration date which can
  be set through questionares or through the sysop.  All security classes
  have an expiration class which is the one that will replace them if they
  expire.  So, in this example, user's in the "Paid" security class might
  return to "Demo" after 6 months.  Some systems keep the user's security
  class secret, (there is no real need for the users to know) other's make
  it information quickly available to them, its your choice.  However users
  in a class such as "Demo" should be informed that they have limited access
  until they send in their money.
    How you setup your security classes is entirely up to you, and defines
  a great deal of how your BBS System will operate.  Security classes
  control many things such as a user's time-limit per-day, and the minimum
  amount of credits they can have per-day (explained more in a moment).
  Before you start defining each security class (By selecting it and pressing
  ENTER or RETURN), figure out how you want your system's security designed
  and create all the necissary classes.  You also need 2 security classes
  for yourself and other sysop users, "Sysop" and "Master".  A MASTER sysop
  is one which can assign other sysops.  A regular sysop cannot modify any
  other SYSOP'S account.  Normally you will have only one master sysop,
  probably yourself.

  [ Security Class ]

  Security Class Name:

    This is what sysops will refer the security class as.  Throughout your
  system and your sysop menu you will use this name to identify the security
  class.

  Door Access Level:

    This is a numeric security level.  Many doors (Any door which operates
  using Door.Sys) use just a number in place of security class.  In those
  situations, a number above 1000 might be any sysop user, and above 2000
  as a master sysop.  The exact settings depend on the doors themselves.
  This value is usually not used by doors, however it can also be used in
  your menuing system if you wish.  You can select what options the users
  may access through this number.

  Sysop Access:                          [Select Box]

    None denies users access to sysop functions.
    Sysop grants normal sysop access to this security class.  The user can
  modify other user accounts, EXCEPT the accounts belonging to OTHER SYSOPS.
    Master grants full sysop access to this security class.  The user can
  modify any account, including other sysops (Normally YOU will be the only
  master sysop on your system.)

  Maximum total time per-day:

    This sets, in minutes, how long the user may use your system each day
  before being disconnected and denied access for the rest of the day.  In
  some systems, this is the prime facter used to control how busy the system
  becomes.  If this setting is too high, and your users find lots to do on
  your system, other users may become frustrated waiting for the "BUSY"
  signal to clear.  On the other hand, if this setting is too low, the other
  users may become frustrated by not enought time to do what they want on
  your system.  An alternative is to use a "Credit system" as explained in a
  moment.  You can set this to 999 to grant virtually unlimited access to
  your system (avoid passing 999).

  Maximum time per-call:

    This sets, in minutes, how long the user may use your system on each call
  before being disconnected and asked to call back later.  A class such
  as DEMO might use this setting to "interrupt" users and force them to
  call back every few minutes until their maximum time per-day is used up
  or their maximum calls are used up (Explained next).  Keep in mind that
  the user's time PER-DAY takes priority over this.  If the user has less
  time per-day left than per-call, the time PER-DAY is used instead.

  Maximum calls per-day:

    This sets the number of times a user in this security class may call
  each day before being refused access.  This can be used with maximum
  time per-call to limit a user's daily calls and time.  If the user has no
  time left for the day, the user is refused access regardless of this
  setting.  If the user runs out of calls for the day, the user is also
  refused access, regardless of how much time they have left for the day.

  Credit LOW Before downgrading:

    Normally set to -1, if set to any other number then the user will be
  downgraded to another security class as soon as their # of credits drops
  below this number.

  Downgrade set after dropping below LOW:

    This is the new security set the user will be given if they drop below
  the value set above (if that value isn't -1.)

  Maximum members in group to join:           [Currently Ignored]
  Days in group before user may change:       [Currently Ignored]
  Cost of joining a new group:                [Currently Ignored]
  Days waiting for votes before processing:   [Currently Ignored]

  Credits given to user each day:

    This value specifies how many credits a user can be given each day.  If
  they have a number higher than this, they will NOT be given ANY credits for
  that day.

  Submenu levels:                             [Currently Ignored]
  Maximum KB user may download per-day:
  Maximum FILES user may download per-day:
  Maximum KB user may download per uploaded:
  Maximum FILES user may download per uploaded:
  Upload access to file areas:                  -Configure-

    This option lets you control which file areas this security class can
  upload to.  Normally, users can upload to the same areas they can download
  from, when using LightSpeed.

  Download access to file areas:                -Configure-

    This option lets you control which file areas this security class can
  download to.

  Access to mail areas:                         -Configure-

    This option lets you control which mail areas this security class can
  read and write messages in.

  [ Mail System Setup ]

    A BBS system's mail is catagorized by its MAIL AREA.  Sometimes different
  mail areas can have different settings, however this is not often needed.
  Common mail area names might be "General Mail", "Technical", "Astrology",
  "HAM Radio", and "LightSpeed-related".  Mail areas are also needed when
  operating with nets such as FIDO, internet, or LaserLinks, however such
  nets are not yet supported by LightSpeed.

  [ Mail Area ]

  Mail Area Name:

    This is what the area will be known as.  This is the only part of the
  mail areas that the users will ever see.

  Maximum Lines in a message:

    This sets the longest message a user can enter in this area.  Normally
  the highest setting of 150 is fine.

  Menu Set:

    These specify a number by which your menuing system can select this area
  and all other areas listed in the same set.  See Ls.Doc for more
  information.  A setting of 0 here indicates ALL menu sets.  Unless you
  support menu sets in your menuing system, leave this set to 0.

  Net Id:

    These will later be used by LaserLinks, but for now leave them set to 0.

  [ File System Setup ]

    A BBS system's files are catagorized by its FILE AREA.  By catagorizing
  files, users can search through only the files they are interested in
  instead of having to sort through thousands of files they don't care about.
  Some typical file areas might be:  "General Files", "Shareware Games",
  "BBS Utilities", "C/C++ Related", and "Doom Related".

  [ File Area ]

  File Area Name:

    This is what the area will be known as.  This is what gives the file
  areas their catagorizing effect.

  % of DL Credits given to uploader:



  Maximum Lines in a message:

    This sets the longest message a user can enter in this area.  Normally
  the highest setting of 150 is fine.

  Menu Set:

    These specify a number by which your menuing system can select this area
  and all other areas listed in the same set.  See Ls.Doc for more
  information.  A setting of 0 here indicates ALL menu sets.  Unless you
  support menu sets in your menuing system, leave this set to 0.

  Net Id:

    These will later be used by LaserLinks, but for now leave them set to 0.

  Upload Access:

    Select this to get a screen listing your security classes.  You can
  then turn on or off each security class's ability to upload to this file
  area.

  Download Access:

    Select this to get a screen listing your security classes.  You can
  then turn on or off each security class's ability to download and list
  files in this file area.

  Path to files:

    This gives the path holding the files for this file area.  You need not
  use all 6 path options, but you must have at least one.  It is recommended
  that you keep all your BBS's files in subdirectories under a directory
  named \BBS.  For example, for a file area named [Games] set your path to
  \Bbs\Games (you may need to include the drive letter.)  And then for
  another file area named [Programming] set your path to \Bbs\Program.
  Finally, you might create a [General Files] area and set its path to just
  \Bbs.
     All uploads to a file area are placed in the first path given (the
  topmost one), if uploads to this area are allowed (controlled by "Upload
  Access").

  [ System Events Setup ]

    Warning:  System Events are disabled in the Trial edition of LightSpeed.
    LightSpeed is capable of performing various operations at specified
  times on a regular basis.  These are called "events".  An event can be
  setup for any days of the week you wish, and will be run once a day on
  the days you've selected.
    All LightSpeed BBSes should have at least ONE event, the "daily
  maintenance" event.  This event should be run once a day probably in
  hours of the day less used (such as 5am.)  There is nothing that FORCES
  you to have this event, your BBS can run without it, however if you run
  the MAINT companion program at least once a week, it will significantly
  improve LightSpeed's disk space usage and speed.  Most systems can run
  MAINT once a day, however once a week is fine.  The "daily maintenance"
  event is already setup when you purchase LightSpeed.
    When modifying System Events using LSConfig, there are 3 screens
  involved.  The first is the node selection screen, in the window named
  "System Events Setup".  From this window, you can only SELECT a node to
  modify the events on.  Events are always managed by-node.
    The second window is named "Events Setup" and appears after you have
  selected a node.  This window lets you insert, delete, and move (Ctrl)
  events.  Select an event to modify its characteristics.

  [ System Events ]

  Days of week (Space, 0, or dash=Off)       SMTWTFS

    This option lets you control which days of the week the event will
  occur on.  Under the letter of the day (S=Sunday, M=Monday, T=Tuesday,
  W=Wednesday, T=Thursday, F=Friday, and S=Saturday) place any letter or
  symbol other than a SPACE, a 0, or a dash to enable that day.  To disable
  that day, place a SPACE, 0, or a dash there instead.

  Time to execute (24hr format):

    This specifies which time of day the event will occur.  In 24 hour
  format, the time 14:30 becomes 2:30pm but 2:30 becomes 2:30am.

  Event Style:

    This specifies how the event will occur.  "Inactivity" events will wait
  until 15 minutes without calls has passed before executing.  Inactivity
  events ignore the "Time to execute" specified above, but will be "forced"
  at 11:00 Pm if they have not yet executed.  "Nearest call to time" events
  will execute at the "Time to execute" if no-one is using the system at
  that time.  If a user is using the system during the time, then the event
  will occur immediately after the user disconnects.  "Force at set time"
  events will occur at the "Time to execute" always, if a user is using the
  system at that time then their time will be lowered so that they will
  disconnected in time for the event to occur (they will be informed that
  a system event is cutting into their time.)
    Warning:  All events are "NEAREST CALL TO TIME" right now, the other
  two modes will be added in the next version of LightSpeed.  LightSpeed
  ignores this setting.

  Event Type (From above list):

    Enter one of the 4 numbers listed to select what the event will do when
  it occurs.  Turning the sysop page on and off controls whether users can
  page the sysop.  The sysop page can also be controlled by pressing F4 in
  LightSpeed at any time, and the sound can be controlled by pressing F3.
  Running a batch file is the most common type of event.  "Daily Maintenance"
  events normally run a batch file called "Daily.Bat" in your LightSpeed
  directory (you may name the batch file whatever you want.)  LaserLink
  calls are disabled and most likely will crash your system if you attempt
  to use them at this time.